---

This section details on the original issue you should resolve

<issue_title>[API Proposal]: DecompressionMethods.Zstd for web requests</issue_title>
<issue_description>### Background and motivation

DecompressionMethods auto-decoding was last expanded with Brotli. Since then, some web servers started serving content using ZSTD compression instead. As such, it'd be appropriate for .NET to include the ability to handle such encoding out of the box.

CURL supports this starting with version 7.72.0, released in August 2020.
Cloudflare supports this since last September.

API Proposal

namespace System.Net;

[Flags]
public enum DecompressionMethods
{
    None = 0,
    All = ~None
    GZip = 0x1,
    Deflate = 0x2,
    Brotli = 0x4,
+   Zstandard = 0x8,
}

API Usage

var handler = new HttpClientHandler
{
    AutomaticDecompression = DecompressionMethods.GZip | DecompressionMethods.Zstandard
};

Alternative Designs

Zstd instead of Zstandard?

The name used for encoding headers is zstd and the media type is application/zstd, while the proposed compression APIs are using Zstandard.

Similar with Brotli where br is used for headers, but we call the APIs Brotli.

Risks

Requires shipping Zstd in System.Compression.Native.</issue_description>

Comments on the Issue (you are @copilot in this section)

@stephentoub This is blocked on https://github.com//issues/59591. @MihaZupan Seems like a reasonable thing to add whenever #59591 happens @bartonjs [Video](https://www.youtube.com/watch?v=NzqIFvMFxWg&t=1h4m36s)

• We think Zstandard is a better name that Zstd

namespace System.Net;

[Flags]
public enum DecompressionMethods
{
    None = 0,
    All = ~None
    GZip = 0x1,
    Deflate = 0x2,
    Brotli = 0x4,
+   Zstandard = 0x8,
}
```</body></comment_new>
</comments>